Updating content within a container document for user groups

ABSTRACT

A computer-implemented system and method to distribute a content document with security, customization, and scalability is provided. One or more servers provides a customizable content document associated with a first entity, enables a second entity to specify content to be included for users associated with the entity in the customizable content document, and delivers the customized content document incorporating the specified content in a secure manner to users associated with the second entity.

This application claims the benefit of U.S. Provisional Application Ser.No. 60/835,861, filed Aug. 7, 2006 and U.S. Provisional Application Ser.No. 60/863,600 filed Oct. 31, 2006.

BACKGROUND

Embodiments of the present invention relate to digital data processingfor serving content over a network.

Portals enable users to personalize content on the portal. Portals areoffered from a portal developer directly to an end user, and do notprovide a means for a third party to add value. Portals cannot be easilymass-produced in a customizable way for large numbers of portalproviders. Moreover, the content that a portal permits an end user toincorporate is usually limited and specified by the portal provider.

These and other drawbacks exist with current systems.

SUMMARY

The present specification discloses various embodiments of technologiesfor a third-party service of securely serving arbitrarily selectable anddynamic content to users on a scalable basis. Embodiments featuremethods, systems, apparatus, including computer program productapparatus.

Accordingly, various exemplary embodiments of the present inventions maybe directed to a method that includes providing a customizable contentdocument associated with a first entity, enabling a second entity tospecify content to be included for users associated with the entity inthe customizable content document, and delivering the customized contentdocument incorporating the specified content in a secure manner to usersassociated with the second entity.

Various exemplary embodiments may also be directed to a method thatincludes receiving one or more selections associated with a user group,and serving a user a container document. In these embodiments, the oneor more selections identify content to be served to users associatedwith the user group for one or more container documents and thecontainer document includes content identified by the one or moreselections for the user group with which a user is associated. Also, thecontent is incorporated securely into the container document.

Various exemplary embodiments may also be directed to a method thatincludes receiving one or more selections associated with a user group,and transmitting the selections to a container server system that servesa container document to users of the user group based on a request forthe content. In these embodiments, the one or more selections identifycontent to be served to users associated with the user group for one ormore container documents.

Various exemplary embodiments may also be directed to a system thatserves content in a container document. The system includes a server toreceive a request for a container document, determine whether therequest is for a container document associated with a user group,request configuration information from a configuration server based on adetermination that the request is for a container document associatedwith a user group, receive the configuration information from theconfiguration server, and serve the requested container document usingthe configuration information. In these embodiments, the configurationserver enables configuration of at least a portion of a containerdocument and the container document is associated with a user group.

Various exemplary embodiments may also be directed to a method thatincludes receiving a request for a container document, determiningwhether the request is for a container document associated with a usergroup, requesting configuration information based on a determinationthat the request is for a container document associated with a usergroup, receiving the configuration information, and serving thecontainer document using the configuration information. In theseembodiments, the configuration information defines at least a portion ofthe container document associated with the user group.

Various exemplary embodiments may also be directed to a method thatincludes receiving a request for a container document, determiningwhether the request is for a container document associated with a usergroup, determining whether a requestor of the request is associated witha level of status within the user group among a plurality of levels ofstatus within the user group, determining the level of status of therequester based on a determination that the requestor is associated witha level of status within the user group, requesting configurationinformation based on a determination that the container document isassociated with a user group and the level of status, receiving theconfiguration information, and serving the container document using theconfiguration information.

Various exemplary embodiments may also be directed to a method thatincludes receiving a request for a container document, determiningwhether the request is for a container document associated with a usergroup, determining a location associated with the request, requestingconfiguration information based on a determination that the containerdocument is associated with a user group and the location, receiving theconfiguration information, and serving the container document using theconfiguration information.

Various exemplary embodiments may also be directed to a system thatserves content in a container document. This system includes a server toreceive a request for a container document, determine whether therequest is for a container document associated with a user group,determine whether a requestor of the request is associated with a levelof status within the user group among a plurality of levels of statuswithin the user group, determine the level of status of the requestorbased on a determination that the requestor is associated with a levelof status within the user group, request configuration information froma configuration server based on a determination that the request is fora container document associated with a user group and the level ofstatus, receive the configuration information from the configurationserver, and serve the requested container document using theconfiguration information. In these embodiments, the configurationserver enables configuration of at least a portion of a containerdocument, and the container document is associated with a user group.

Various exemplary embodiments may also be directed to a system thatserves content in a container document. This system includes a server toreceive a request for a container document, determine whether therequest is for a container document associated with a user group,determine a location associated with the request, request configurationinformation from a configuration server based on a determination thatthe request is for a container document associated with a user group andthe location, receive the configuration information from theconfiguration server, and serve the requested container document usingthe configuration information. In these embodiments, the configurationserver enables configuration of at least a portion of a containerdocument and the container document is associated with a user group.

Various exemplary embodiments may also be directed to acomputer-accessible medium encoded with computer program code. Thecomputer program code is effective to receive a request for a containerdocument, determine whether the request is for a container documentassociated with a user group, determine whether a requestor of therequest is associated with a level of status within the user group amonga plurality of levels of status within the user group, determine thelevel of status of the requestor based on a determination that therequestor is associated with a level of status within the user group,request configuration information based on a determination that thecontainer document is associated with a user group and the level ofstatus, receive the configuration information, and serve the containerdocument using the configuration information.

Various exemplary embodiments may also be directed to acomputer-accessible medium encoded with computer program code. Thecomputer program code is effective to receive a request for a containerdocument, determine whether the request is for a container documentassociated with a user group, determine a location associated with therequest, request configuration information based on a determination thatthe container document is associated with a user group and the location,receive the configuration information, and serve the container documentusing the configuration information.

Various exemplary embodiments may also be directed to a method thatincludes authenticating a user based on the user's association with auser group, providing the user with an application, receiving input fromthe user regarding configuring the container document associated withthe user group, providing an actual representation of the containerdocument to the user based on the received input, and publishing thecontainer document. In these embodiments, the application enables theuser to configure a container document associated with the user group.

Various exemplary embodiments may also be directed to a method thatincludes registering components of a user interface, registering eventsregarding configuration of a container document, associating registeredcomponents with registered events, receiving information associated withregistered event that has occurred for one of the registered components,and providing the information associated with registered event to allother associated components. In these examples, the user interface isassociated with configuring a container document of behalf of a usergroup.

Various exemplary embodiments may also be directed to a system thatincludes a device to register components of a user interface, registerevents regarding configuration of a container document, associateregistered components with registered events, receive informationassociated with registered event that has occurred for one of theregistered components from the user interface, and provide theinformation associated with registered event to all other associatedcomponents.

Other embodiments may be considered.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1( a) depicts an overview of participating entities in a system andmethod provided according to various embodiments of the presentinvention.

FIG. 1( b) depicts an illustrative process for obtaining customizationsfrom users and user groups according to various embodiments of thepresent invention.

FIG. 1( c) depicts an overall system architecture according to variousembodiments of the present invention.

FIG. 2 depicts an illustrative container document according to variousembodiments of the present invention.

FIG. 3 depicts an illustrative configuration server according to variousembodiments of the present invention.

FIG. 4 depicts an illustrative process for determining a validatoraccording to various embodiments of the present invention.

FIG. 5 depicts an illustrative process for configuring a personalizedcontainer document according to various embodiments of the presentinvention.

FIG. 6 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 7 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 8 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 9 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 10 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 11 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 12 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 13 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 14 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 15 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 16 depicts an illustrative process for serving a personalizedcontainer document according to various embodiments of the presentinvention.

FIG. 17 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 18 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 19 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 20 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 21 depicts an illustrative application interface according tovarious embodiments of the present invention.

FIG. 22 depicts an illustrative process for serving a personalizedcontainer document according to various embodiments of the presentinvention.

DETAILED DESCRIPTION

Overview of the Third Party Service

One embodiment of the present invention involves a third party serviceof securely serving arbitrarily selectable and dynamic content to userson a scalable basis. For example, the one embodiment involves four kindsof entities: (1) a hosted server system (e.g., Google's PersonalizedHome Page Server) that distributes a highly configurable, dynamic andsecure container document (e.g., a portal page such as Google'sPersonalized Home Page) to partners or other user groups; (2) partners,wherein each partner provides configuration through selection ofarbitrary and dynamic content that it wants its users to see in thecontainer document and enables its end users to further customize thecontent; (3) end users associated with a partner that may select furthercustomizations including additional arbitrary and dynamic content; and(4) content providers. These parties interact with the host serversystem in a secure and scalable way. The end users then receive from thescalable hosted server system a container document that has beenconfigured according to the multiple levels of configuration and thatincludes the arbitrarily selected content (including both dynamic andstatic content) incorporated in a secure manner.

Features of the Service

Some of the features of this service and system include third partyservicing, security, arbitrary selectability, dynamic content,scalability, multiple levels of configurability, and dynamic provisionof container documents.

Third Party Servicing: The service may be considered a “third partyservice” in that a hosted server system (e.g., Google) acts as a thirdparty with respect to (i) end users being served content (ii) an entitywhich specifies the content available to the end users, and (iii)content providers. The entity specifying content is typically a usergroup, such as a partner. When the term partner is used in the instantspecification, it should be understood to apply equally to other usergroups and when the term user group is used, it should be understood toapply to a partner as one example. A company and its customers areexamples of the partner entity and end users, respectively. A universityand its students are also examples of the partner entity and its endusers. So, a company can provide a configured home page experience forits users and select the content it wants its users to see on thatconfigured home page. It does so by leveraging the hosted serversystem's service of the container document. In other words, the partnermay provide this service without providing the technology to output theconfigured home page that is provided by the hosted server system. Asused in the instant specification, the term content provider refers to asource of information. Examples of a content provider include but arenot limited to a provider of a module, a news feed, a source of trafficinformation, a source of financial information, and/or a source ofentertainment information.

Security: The container document may be secure despite the arbitrarilyselectable and dynamic content (i.e., the hosted server system does notlimit the initial selections made by the third party or users). Forexample, a partner may select a module created by an entity unknown tothe hosted server system. The hosted server system may render acontainer document that includes the unknown entity's module byimplementing security features to avoid having to approve each moduleahead of its selection. Security may be implemented bycompartmentalization, encapsulation (e.g., through the use of IFRAMEtechniques as described in more detail below) and/or input filtering(e.g., blacklisting, whitelisting, etc. of content). In this context,compartmentalization involves limiting the impact of an attack by amalicious or vulnerable (e.g., unsafe) partner or end user to thecustomized container documents associated with the partner or end userand not other compartments or accounts available from the systemassociated with the same login or identity used to access the customizedcontainer document.

Compartmentalization is a key component of the security because thesecurity of the third party is not compromised despite the fact that thecontent is arbitrarily selectable and dynamic. If the userauthentication is compromised, e.g. by a malicious partner or due to apartner vulnerability (XSS, etc.), then only the user's personalizedpage is compromised. The attacker can't gain access to the user's searchhistory or email messages or other “compartments,” even after asuccessful attack. The security features implemented enable the partnerand its users to configure their experience while leveraging the hostedserver system's platform.

Arbitrary Selectability: The security features described enable thesystem to permit arbitrary selection of content. The partner entity andassociated users may select, from any content provider (e.g., sourcesincluding the hosted server system, the third party and/or other sourcesof content) content to be made available for serving to users associatedwith the partner entity. A partner may choose to limit the selectionsavailable to its end users or not. The system may avoid use of apre-approved list of content providers in this way. Content may be of awide variety of input types as well, as detailed below.

Dynamic Content: The content selected may be dynamic content, staticcontent or both. The content may also be programmatic.

Scalability: The hosted server system provides this service from ascalable platform achieved, for example, through segmenting data for usewith a non-relational database server. This solution balances scale andease of data coherency. Certain types of non-relational data storagesystems allow massively scalable write operations. For example, adatabase that does not provide transaction or locking support whilestoring time-series data with entries is not considered a relationaldatabase because an entry for the relation (Column1Value, Column2Value,. . . ) is not unique, but rather a time series. By using such anon-relational database, the system may become massively scalable. Mostwrite operations to shared data are initiated from a small set of users(one or a few partner administrators), while read operations areinitiated widely (e.g., each time an end-users requests a page, thetemplate for an associated container document may be loaded).Scalability may also be achieved using a traditional relationaldatabase, highly replicated for scalable read operations, with masterfailover to enable high availability. Using this approach may increaseoverhead and add complexity and latency to the system.

Nevertheless, a simple non-relational storage system as described aboveenables a system and service for distributing configurable containerdocuments to perform well on a massive scale. Such a system and serviceinvolves centralized writing and decentralized reads, high throughput(scalability and simplicity) and high availability (supportingfailover). The database structure described enables implementation atmuch lower cost (fewer servers needed at a given scale) than otheralternatives such as the highly-replicated relational database example.

Multiple Levels of Configurability: The content served may be configuredby the partner/user group, which configuration can specify constraintsunder which end users associated with the entity may further configurethe content.

Dynamic Provision of Container Documents: Partner/user groups may selecta uniquely indexed partner domain that may be stored in a dynamic tableby the hosted server system. By storing this uniquely indexed partnerdomain, the hosted server system may dynamically provide containerdocuments associated with a partner/user group in a highly scalablemanner.

Exemplary embodiments of the invention are discussed in detail below.While specific exemplary embodiments are discussed, it should beunderstood that this is done for illustration purposes only. A personskilled in the relevant art will recognize that other components andconfiguration can be used without departing from the spirit and scope ofthe invention.

Advantages of the Service

Some of the advantages this service provides include that an entity(e.g., partner or user group) such as a corporation, university club,merchant, service provider, etc. may effect its branding scheme usingthe service while not having to serve the content. It providestremendous flexibility in what content is served to users associatedwith the entity. The service also provides the entity with a mechanismto offer a unique content offering to their the users associated withthe entity.

Also, the entity using this service converts a cost center into a profitcenter. An entity, such as a corporation, usually pays to have contentserved to its customers. With the above-described service, thecorporation turns a profit by including content that generates revenue,such as content that serves advertisements that pay those who serve theadvertisements on various payment bases.

Also, the service is easy to use through an intuitive and easy-to-useinterface by which a human operator associated with the partner entity(e.g., a representative) configures content, at either the entity levelor the end user level.

Overview of a System and its Operation

FIG. 1( a) depicts an overview of various entities involved in thissystem and service. The service and system described may be implementedusing a hosted server system 10 providing service to a partner system 40over a network 26 (e.g., the Internet) in cooperation with one or morecontent providers 31. Partner system 40 may, through the use of partneradmin users 17, provide selections and configurations to hosted serversystem 10 indicating a domain associated with the partner system, theauthentication method for one or more partner end users, and the contentto be provided in a container document served by hosted server system 10to one or more partner end users 11.

The hosted server system 10 may operate with a distribution server 13 todistribute the service to one or more partner systems. A data storagesystem 20 may be provided that stores container data, user data, andpartner data. That data may be used by hosted server system 10 toconfigure the container document for users based on configurations setup by the partner and, if provided, each partner end user 11. Ingeneral, partner admin users 17 have administrative rights whereaspartner end users 11 do not. Partner admin users 17, can, for example,control the authentication methods for authenticating partner end users11 and which content provider would be available for selection bypartner end users 11 and, furthermore, the degree of configurability.

FIG. 1( b) provides a diagram illustrating actions that may be involvedin this service. In block 102, a partner or user group establishes arelationship with the hosted server system. The partner may be acompany, university, club or other organization that desires to providea customized experience for its users. In block 104, a partner adminuser may then configure the container document, such as an Internetportal page or personalized home page in a number of ways, all detailedbelow. Customization can include, for example, the partner'sspecification of constraints that one of its end users is subject to forselecting content and/or for configuring a personal Web page. Note thatthe partner can specify different constraints for different end users.The system may then make the configured container document available tousers associated with the partner.

In block 106, partner end users may be identified by the partner to thehost system in some way. Partner end users may include employees of acompany, students of a university or other school, members of a club,subscribers to a service, etc. In block 108, a partner end user may beserved a default partner-configured container document. This defaultpartner-configured container document includes a first level of contentand/or configurations that is selected by the partner to be served toits users. In block 110, an end user may provide configurations for theconfigured container document. This configured container documentincludes an additional level of content selections and/or configurationsthat are based on the end user's desires.

Specific Implementation Features

With the overall general framework in mind, there are a number ofimplementation features that may be included in this system and serviceincluding multiple levels of configuration, content freezing,incorporation of multiple types of modules, multiple channels of accessto the configured container document, use of preferences and useridentification to change content modules and content within modules,incorporation of search or other revenue generating modules,internationalization of modules, data driven container documentimplementations, use of subscription-based modules, modification of adefault container document on the fly according to partnerconfigurations, live preview of customizations and live updates togenerated configured container documents. Each implementation feature isdescribed below and in the more detailed explanations later in thedocument.

Multiple levels of configurations control the user experience: a partnermay set one level of configuration and/or preference, including whatmodules are to be included in the default partner configured containerdocument (e.g., the partner wants a weather module, a traffic module, astock module and a calculator module), any values for inputs to themodules (providing a zip code for the weather and traffic or a list ofstocks for the stock module), color, skin style, positioning of modulesand many others as shown in the illustrative pages below, and what, ifany, modules may be frozen. If a partner makes any changes to itsconfigurations, they may automatically apply to all configured containerdocuments for all end users associated with the partner. The manner of apartner providing configuration/customization information is detailedbelow. End users may then specify a second level ofconfiguration/customization, with such end user configurations andpartner configurations being applied to the partner-configured containerdocument for that end user.

Content Freeze: One specific type of partner configuration may be acontent freeze. The service provides techniques that the partner may useto disable configurability of all or only a portion of content served toend users. The content chosen for disabling is, in essence, frozen inthat it cannot be further configured by a partner end user. Note thatcontent freeze can but does not necessarily freeze dynamic content,which can be still implemented in a frozen portion of a personalized Webpage, for example. (That is, freezing a portion of the page preventsfurther configuration of the portion but allows the portion to includedynamic content.) A column of otherwise configurable content of apersonalized web page may be thus frozen, for example. When the partneris in the process of configuring the container document, however, thatdisabled content may not be frozen to the partner administrative userentity. This feature can be implemented by CGI parameters andauthentication techniques. For example, a page request specifying thatthe user is a partner admin user may provide authentication valuesthrough cookies, enabling certain query parameters, so that the hostedserver system provides an unfrozen page, whereas end users associatedwith the partner may receive a version with frozen content.

The service also allows the partner administrator to view the page as ifthe administrator were an unprivileged user. As noted above, the partneradmin user may view the frozen content in an unfrozen context. However,if the partner is to preview the page to determine whether it isproperly configured, the partner may also be able to view the page in afrozen context. The service enables correct context-dependent behaviorusing authentication tokens that are not only used to authenticateaccess to the page, but also to authenticate access to the queryparameters used to enable the context dependent behavior.

Incorporation of multiple types of modules: The system enables partnersand end users to designate a wide variety of modules for incorporation,including RSS modules, remote modules, API-based modules forpersonalized homepages, such as Google Gadget API modules and others.The ability to incorporate these modules is described in greater detailin the attached patent application.

Multiple points of entry into the system: End users may haverelationships with both the partner and the hosted server system.Accordingly, the hosted server system may enable the user to access apartner container document using authentication values associated withan account provided by the hosted server system and/or an accountprovided by the partner. For example, if the hosted server system isGoogle, a user may be able to access a partner-specific personalizedhome page through use of a Google login and password. Also, a user maybe able to access a partner-specific personalized home page through useof a login and password associated with the partner. Either useridentification may be used to receive the partner-specific containerdocument. Also, during configuration of partner container documents, thepartner admin user may select an authentication method forauthenticating end users from a list of predetermined authenticationmethods that the system may employ. In one implementation, for example,if the system permits three authentication methods, the partner adminmay choose only one of the three. Alternatively, the partner admin mayallow more than one authentication method. The system then authenticatesbased on the method selected by the admin user. For example, the partneradmin user may choose to have all partner end users authenticate via anaccount provided by the hosted server system. That authentication may beused even if the user also has an account with the partner. In anotherexample, the partner admin user may chose to have all partner end usersauthenticate via an account provided by the partner. That authenticationmay be used instead of an account provided by the hosted server system.Other authentication schemes such as, e.g., anonymous authenticationmethods that rely only on a cookie, may be selected.

Controlled experience based on registration: Some modules may bemodified based on registrations or other forms of authentication. Forexample, a partner that is a computer manufacturer may incorporate ahelp module on its partner-customized home page. The content in the helpmodule may vary depending on registration levels of the user (e.g.,whether the user signed up for ongoing customer support, what level ofsupport they requested, etc.).

Commerce in the modules: The controlled experience may enable thepartner to monetize the partner container document. A user may becharged a subscription fee by the partner to access certain modules orcontent within the modules. For example, the partner may offer a musicmodule. A subscription to the partner's music module may enable the userto choose certain selections of music to hear based on subscriptions.Also, within the music module, the partner may offer differentsubscriptions. For example, one subscription may permit an end user tolisten to music, while another may permit the user to listen to anddownload music.

Search box module: One of the modules that a partner may select may be asearch module that leads to a hosted search page that servesadvertisements (e.g., linked to an existing AdSense for Search). Thedisplay of advertisements in association with the search module providesanother way for the partner to monetize the partner container document.In one example, the search box module may be a required module of acontainer document.

Selective and automatic internationalization: The container document mayinternationalize the container document based onconfigurations/customizations provided by the partner or its users.

Data-driven container documents: The container document for a partnermay be designed to generate a common template with different contentbased on data input to the system (e.g., WiFi detection is used to havethe partner container document modified depending on location). Thesystem may also provide different localized partner container documents.

Modification of a default container document: The system may provide adefault container document that the partner then configures. Thecontainer document server and/or hosted server system then cooperateswith an interface provided to ensure that the content provided meets thepartner configuration selections in a safe manner.

Fully-functional preview: A partner admin user interacting with theconfiguration interface may view a live version of the containerdocument based on configuration information being input and what theuser sees is the container document that includes the actual content andmodules from the hosted server system (e.g., not just a mock-up). Thesystem may further allow editing of a module from within the previewpage.

Live updates to container documents and live preview: Use of a centralrepository of events with associated interested parties enables thesystem to update live previews and live container documents based onchanges related to those items. The repository may track what userinterfaces or modules are to be notified of events that alter theirperformance and then may notify them immediately. As an example, if apartner admin user is requesting a change to the background color of thepartner customized container document, as soon as that partner adminuser selects a color swatch, the background automatically changes(rather than requiring the user to say “Apply” for example) for a real,live preview.

Each of these features will be understood in greater detail in thecontext of the following systems, methods and example pages discussedbelow.

Multiple Levels of Configurability and Content Freezing

One implementation feature for this service and system relates tomultiple levels of configurability of the content of a containerdocument. An example container document is next described along with anexample system that may be used to enable a partner and end users toprovide configuration information.

One example of a container document is a personalized portal page thatis associated with a user of a partner or other user group. A portion ofthe content on the personalized portal page may be predefined by thepartner/user group, and a portion of the personalized portal page may beconfigured and customized by the end user.

The container document “contains” one or more modules. Any number of themodules or other content “contained” within a container document may bepredefined by a representative of a user group. As used herein, the term“container document” or “container” should be understood to include apersonalized homepage of a website, a portal page associated with a usergroup, a sidebar, toolbar element that incorporates one or more suchmodules, a page hosted by a site, a document capable of renderingmodules (e.g., any document capable of rendering HTML code or XML code)in the format of the module (e.g., XML). Also, the container documentmay be a website of another entity that incorporates modules provided tothe website from a syndication system.

As used herein, the term “module” may be understood to refer to a pieceof software and/or hardware that renders data for use in a containerdocument. Modules may be personalized to user preferences, preferencesof the container, preferences of the environment or other inputs,including preferences defined by the user group, for example. A modulespecification may be understood to include a set of instructions used torender data for the container document using elements that have beenpredefined.

It should be appreciated that various forms of the container documentmay exist but one such illustrative example is depicted in FIG. 2. FIG.2 depicts a container page 200 with a plurality of modules that havebeen incorporated into the container document using IFRAME and inlineHTML techniques. These IFRAMES may allow the hosted server system toencapsulate the arbitrarily selected content defined by the user group.In one example, modules may also be served in the container documentwith or without an encapsulation layer. Encapsulation layers may provideuseful functions in many types of systems, (e.g., serving a modulewithin an IFRAME in an HTML document provides a security enhancingbarrier). Other applications may prefer to serve module content withoutsuch an encapsulating layer (e.g., for improved performance or ease oflayout or content management).

FIG. 2 depicts a plurality of modules and other content within containerdocument 200 including a header 201, a logo 202, a search box 203, usergroup content 204, an “add content” element 205, a user-selected module206, a remote module 207, a remote module 208, and a remote module 209.Different formats for the various modules may exist depending upon, forexample, the specification of the creator of the module and/or thedefinition of the module by a representative of the user group. Asdepicted, some modules may provide scroll bars, and others may not. Somemodules may have different sizes or shapes compared to other modules. Inaddition, some modules may offer the opportunity for the user to editthe display preferences and/or per-use data associated with the module.(See, for example, modules 206, 208, and 209 that provide an edit link.)For example, if the module relates to a weather module, the user may beprovided the opportunity to edit the city or zip code for which theweather is displayed in that module.

A portion of the content on the container page 200 may be created and/orpredefined by a user group and/or a representative of a user group. Forexample, the header 201 may contain links 201 a that are associated withthe user group. Logo 202 may also be a logo that is associated with theuser group. User group content 204 may be created and/or defined by theuser group and optionally locked or frozen (described below) so thatusers of the personalized container document cannot remove, edit or adduser group content.

Header 201 may comprise HTML and/or XML code to create, for example, abanner on container page 200. Header 201 may include links 201 a thatmay be associated with the user group. For example, where a user groupis associated with computer hardware provider, links 201 a may includelinks to particular services provided by the computer hardware provider(e.g., service and support) and links to particular goods provided bythe computer hardware provider (e.g., desktops, laptops, peripherals,and/or printers). Where a user group is associated with an InternetService Provider (ISP), links 201 a may include links to email, contentdriven pages provided by the ISP (e.g., sports, finance, shopping,etc.), customer service, and the like.

Search box 203 may include a text field 203 a and a search button 203 b,where a user can enter text into text field 203 a, and activate (e.g.,click on) search button 203 b which initiates a search engine that maybe associated with container page 200 to search for the text enteredinto text field 203 a. When search results are returned, a search engineassociated with the container document may track any follow-on actionperformed by the user as will be described in greater detail below.

Container page 200 may contain user group content 204. User groupcontent 204 may include user group modules 204 a-204 c. User groupcontent and user group modules 204 a-204 c may be created and/or definedby the user group. Modules 204 a-204 c may be modules that arespecifically associated with the user group and/or any other unrelatedmodule that may be selected for inclusion into user group content 204. Arepresentative associated with the user group may be grantedadministrative privileges to create and/or define user group content204.

One of the functions provided with this example container document 200is the opportunity for the user to add content to the container pagethrough selecting the “add content” element 205. The content that may beavailable to be added to container page 200 (e.g., the taxonomy) may bedefined and/or restricted by the user group. For example, a user groupmay restrict a user from adding modules of a competitor or any othermodules that may be deemed to be undesirable by the user group.

Upon selecting the “add content” element, the system may offer an enduser the opportunity to interactively indicate an additional module tobe included in the container page based on the taxonomy defined by theuser group, for example. Various forms of an interface to receive thatinput may be provided.

User-selected module 206, and remote modules 207-209 may be a result ofadding content.

Content Freezing

The content added by the user may be placed within container page 200 inaccordance with the preferences of the user. However, the user may berestricted or prevented from placing, moving, or modifying some contentdefined by the user group. In other words, certain portions of thepartner/user group defined container document may be frozen to the user.Thus, the resulting container page 200 may include a portion of thecontainer page that is defined by the user group in accordance withpreferences established by the user group and a portion of the containerpage that is defined by the user in accordance with preferences of theuser. For example, a column of modules or row of modules may be frozenso that the user may not eliminate, move, alter or change their positionand/or content. In addition, certain blank spaces on a partner containerpage may be frozen to prevent a user from adding a module to that blankspace.

Interaction with Container Server System

As described above, the hosted server system 10 may serve a containerdocument to end users of the partner based on partner-specifiedconfigurations and end-user specified configurations. To actuallygenerate a container document with content, a variety of platforms maybe used.

One such platform may be the Remote Module system and the associatedPersonalized Google Homepage system, which is described in detail inco-pending U.S. patent application Ser. No. 11/298,930, filed on Dec.12, 2005, entitled “Remote Module Incorporation Into A ContainerDocument,” the contents of which is attached hereto as Appendix A. (Notethat in the event of an inconsistency between the present disclosure andAppendix A, the present disclosure controls with regard to eachembodiment separately. In the event that the present disclosure andAppendix A are consistent, but of differing scope, the disclosure ofgreater breadth controls with regard to each embodiment separately.)That application details an example hosted server system 10. FIG. 1( c)depicts an overall system diagram that provides a number of systemsoperating with hosted server system 10. Details of an example hostsystem taken from the '930 application are provided later in thisdocument.

To facilitate a partner being able to take advantage of the service, thepartner/user group may enable one or more partner admin users tointeract with a configuration server system that communicates with or ispart of hosted server system 10. An example of such a system is shown aselement 40 in FIG. 1( c). Configuration server system 40 may have aconfiguration server 41, authorization/authentication unit 42, and adata server 43. In addition, one or more user group database systems 44may operate in conjunction with the various units of configurationserver system 40. Configuration server system 40 may connect overnetwork 26 (e.g., the Internet) to hosted server system 10. In oneexample, configuration server 40 may be hosted.

With regard to configuration server system 40, a configuration server 41may be provided to allow representatives of a user group to createand/or define a container document, or a part of a container document(e.g., a set of modules) to be associated with the user group and toenable a partner end user to select/identify an authentication method ormethods to be applied for container documents. Configuration server 41may also communicate with hosted server system 10 to serve a containerdocument to users of the user group.

An authorization/authentication unit 42 may be provided to authenticatethe representative of the user group that may be charged with creatingand/or defining the container document associated with the user group.

A data server 43 may be provided to serve the data that may be displayedon a container document. Data server 43 may store and serve imagesand/or any other data that may be used in a container document, forexample. Data server 43 may also store HTML code for modules that may bedesigned specifically for users of the user group, for example.

While one configuration is shown in FIG. 1( c), it should be appreciatedby one of ordinary skill in the art that other configurations of thesevarious units may also be possible. For example, the various unitsdepicted within hosted server system 10 may be disposed at variouslocations around network 26 or at various points on several networks.Similarly, the various units depicted within configuration server system40 may also be disposed around various locations around network 26,including within, for example, hosted server system 10. In addition,whereas a single hosted server system 10 and a single configurationserver system 40 are depicted, it should be appreciated that any numberof each of the units depicted on FIG. 1 may be provided includingnetwork 26.

Illustrative Configuration Server

FIG. 3 depicts an exemplary embodiment of a configuration server 300.Configuration server 300 may be a tool for representatives of the usergroups to create and/or define one or more container documents for usersof the user group and establish an authentication method for users ofthe user group. As shown in FIG. 3, configuration server 300 may includea servlet layer 301, a validation layer 302, an action layer 303, and abackend layer 304.

Configuration server 300 may serve a web application to user systems ofrepresentatives of the user group (e.g., partner admin user 17) toenable those representatives to create and/or define one or morepersonalized container documents for users of the user group.Configuration server 300 may also be a local application run by a user.For security reasons, or to restrict the number of users that haveaccess to the application, a partner may provide the local, standaloneapplication to the representatives for installation on their usersystems, for example. The representatives may be identified as havingadministrative privileges for the user group. These privileges mayenable the representative to receive the web application (or install thelocal application) to create and/or define one or more personalizedcontainer documents for users of the user group. The web applicationreceived (or local application installed) by the representative mayinclude a HTML editor to enable the representative to edit a containerdocument, for example.

Configuration server 300 allows representatives and/or privileged usersto define, for example, an optional banner and/or header across the topof a container document, optionally lock one or more column of modulescontained within the container document, configure a default set ofmodules to appear on a container document, configure a set of availablemodules that may be included on a user's personalized container document(e.g., the taxonomy), configure default options for the modules thatappear on a user's personalized container document, and/or define and/orconfigure the container document in any other manner possible.Configuration server 300 also allows representatives and/or privilegedusers to select a uniquely-indexed partner domain that may be used todynamically provide the container document to users and select anauthentication scheme for authenticating the users.

Servlet layer 301 may execute three exemplary servlets in cooperationwith the application executing on a representative's user system, forexample. In such an embodiment, as will be understood, a servlet mayinclude any program, such as a Web server, a servlet engine, a CGIscript, or a non-Web-based remote configuration program. For example, afirst servlet may be executed to serve a user interface to an authorizeduser of the configuration server. The first servlet may acceptno-parameter HTTP GET requests and may serve an initial HTML interfaceand a JavaScript client to an authorized user, such as a representativeof the user group, for example. Also, the first servlet may retrievedata from a backend interface (e.g., a list of pages available forupdate by the authorized user) and present such data to the user.

A second servlet may be executed to receive updates to one of thecontainer documents, for example. Inputs and outputs may be received andtransmitted, respectively, by this servlet in JavaScript Object Notation(JSON) format. An input parameter may be associated with an “action” andthe value may be a JSON representation of a batch of “action” objects.This servlet may deserialize (e.g., convert the “action” object into aJAVA file) the JSON representation and pass the deserialized parameterto other layers within the configuration server. Also, this servlet maygenerally convert configuration information from its user input format(e.g., JSON) into HTML, XML, Microsoft Word macros, or the like.

A third servlet may be executed to handle data uploads, for example.Data including, but not limited to, images may be received as“mulitpart/form-data,” and may need to be extracted in a mannerdifferent than extracting GET/POST parameters. Once extracted, therequest to upload the data may be passed to other layers within theconfiguration server.

The servlets described above may be accessible only by thoserepresentatives of a user group that are authorized. To receive the webapplication, a user may initially issue a request to the first servlet,be authorized by an authentication/authorization unit, be served a userinterface, and then indirectly issue other requests to other servletsthrough the user interface. Also, to receive the local standaloneapplication, the partner/user group may provide the application on diskor make it available for download by the user. The user may then installthe application and run the application to indirectly issue otherrequests to other servlets through the user interface.

Validation layer 302 may verify the data that is received by theservlets and convert the data for use by other layers of theconfiguration server. For example, servlet layer 301 may accept externalrequests, and because this data is external, it may need to be verifiedas being secure. Further, servlet layer 301 may receive parameters asstrings. When parameters are received as strings, those parameters mayneed to be converted into, for example, typed parameters.

Validation layer 302 may accept “action” objects from the servlet layer301. The “action” objects may provide the requested “action” and astring-string name-value map of parameters required to execute the“action.” Given the “action,” validation layer 302 may determine fromanother layer within the configuration server, what types of parametersare required to execute the “action.” Based on this determination,validation layer 302 may validate the input strings and convert theinput strings to the appropriate type of parameters.

The types of parameters may be represented as “action parameter types.”By representing the types of parameters as “action parameter types,”standard Java-types may be superseded. For example, a uniform resourcelocator (URL) and a block of HTML may be represented in Java as strings.Different validation rules may be applied to these different parameters(e.g., a URL may be well-formed with a recognized scheme and onlycontain valid characters, while HTML may be scrubbed such that it maynot contain JavaScript, that may open security holes). To applydifferent validation rules to different types of parameters, validationlayer 302 may run different “action parameter types” through differentvalidators.

Mapping each “action” to a list of “action parameter types,” may alsoallow validation layer 302 to automatically select which validator isrequired for each “action.” FIG. 4 depicts an exemplary embodiment of aflow chart 400 for automatically selecting which validator may address aspecific “action.” In block 401, the “action” may be determined from the“action” input. In block 402, the types of parameters that are requiredto execute the “action” may be determined. This determination may beaccomplished by another layer within the configuration server.

For each parameter type required to execute the “action,” in block 403,the “action parameter types” may be received. In block 404, thevalidator for the “action parameter type” may be determined. In block405, the string-value of the parameter from the “action” input may bedetermined. In block 406, the string-value may be passed through thevalidator. In block 407, the validator may output a valid Java-typevalue for the corresponding string-value. In block 408, the Java-typevalue may be saved.

One or more methods for validation may be used. For example, simpleparameters (e.g., Boolean expressions) may be parsed using a Booleanfilter, while complex parameters (e.g., objects) may be deserializedinto a Java object. Validation layer 302 may pass validated parametersto action layer 303 for action.

Action layer 303 may execute an “action.” Action layer 303 may receiverequests from validation layer 302 and interact with backend layer 304to execute the “action.”

“Actions” may be registered with an “action manager” so that the“actions” may be executed. In such an embodiment, to register an“action” with the “action manager,” an “action info” object indicating,for example, the java-class and public method containing the logic andthe parameters required to execute the “action,” may be specified. Whenan “action” is registered, the “action manager” may be queried for theparameters required to execute the “action,” and action layer 303 canthen request execution of the “action” and pass those parameters.

As noted above, action layer 303 may interface with backend layer 304 toexecute an “action.” In such an embodiment, when interfacing withbackend layer 304, action layer 303 may cache data received from backendlayer 304. Similarly, action layer may store multiple updates, forexample, before passing the updates to backend layer 304.

Backend layer 304 may provide an interface with backend units in thesystem. Backend units in the system may store and provide access to dataassociated with the user groups and container documents for the usergroups. Such data may include, for example, preferences of the usergroup (e.g., default preferences for a container document), data to mapuser groups to the respective preferences of the user group, loginauthentication and authorization data (including data about authorizedrepresentatives of the user groups), images, content for a portion of apage that may be defined and/or personalized by a user group, and/or anyother data related to user groups, representatives of the user groups,or users of the user groups.

Illustrative Process for Configuring a Container Document

Container documents (e.g., portal pages or personalized portal pages)may be initially configured by a representative of a user group. Also,container documents may initially be configured as a result of groupvoting or meta-group requirements (e.g., groups within a group). Thecontent may also be initially determined as a result of collaborativefiltering. As described above, personalized container documents mayinclude a portion of content that may be created and/or designed and/orconfigured for the user group and a portion of content that may beconfigured by users of the user group. The configurations by the usersof the user group may be limited by the configuration and/or designpresented by the user group.

FIG. 5 depicts an exemplary flow chart 500 which illustrates anexemplary method for designing and configuring a container document. Inblock 501, a relationship with a user group may be established. A usergroup may establish a relationship with a host of the containerdocument, for example. To establish a relationship with a host, a usergroup may identify itself and one or more representatives that may beauthorized to design and/or configure a container document on behalf ofthe user group. In one example, the user group may also establish anaccount with the host. The account may be a Google AdSense account orany other account that may be used to store any data about the usergroup.

Where the user group has a preexisting account with the host, the usergroup may indicate as such and the system may associate the user groupwith the preexisting account. When the user group has been identified,an identifier associated with the user group may be stored in a databasesystem associated with the configuration server. The domain name mayalso be included in a map file, for example, that may map the user groupto data associated with the container documents for the user group.

In one example, the domain name may be selected by the user group. Forexample, the user group may select a domain name such as, e.g.,“start.usergroup.net.” This user group-selected domain name may then bemapped to, for example, a more explicit path such as“partnerpage.host.com/usergroup.net” and this masking/aliasinginformation may be stored by the host server system in a dynamic tableof uniquely-indexed partner domains.

To begin the configuration process, in block 502, a representative ofthe user group may login to a configuration server system, For example,a representative may include a corporate representative of the usergroup, a web master of the user group, a agent of the user groupselected by the user group, or any other person or group of peopleselected to represent the user group for purposes of configuring acontainer document. An authorization/authentication unit may receive alogin request including, for example, a user name and passwordassociated with the representative, determine whether the representativehas administrative privileges for the user group, and grant access tothe configuration server system based on a determination that therepresentative has administrative privileges for the user group.

In block 503, the configuration server system may serve a webapplication to the representative. A representative may be operating aclient device and/or user system capable of providing inputs to the webapplication (or standalone application) to configure a containerdocument or personalized container document. A servlet associated with aconfiguration server may serve the web application to the client deviceand/or user system. The client device may receive the web applicationand execute the web application on the client device. Where theapplication is a standalone application, the standalone application maybe installed and executed on the client device. The web application (orstandalone application) may include, for example, an editor for editingthe header and/or other portions of the container document and othertools for configuring and/or designing a personalized containerdocument. Such other tools may include, for example, an action bar, forreceiving actions to be executed; a tab set, including a layout tab, acolors tab, a color code editor, and other modules; an available contenttab to create custom modules and/or define the module taxonomy; a livepreview pane; a module picker; a header and footer tab; and a URL editortab.

The action bar may include, for example, icons or buttons, that whenactivated, may trigger the execution of an action. Such actions mayinclude save, delete, edit, open file, open blank container document,change format of the container document, display live preview, insertobject or module, and any other like action. The layout tab may includea selection of predefined layouts that, for example, enable the user tofreeze (or lock) a certain portion of the container document or permit auser to control all content on the container document. FIG. 6 depicts anexample application interface 600 including a layout tab 601 inaccordance with an exemplary embodiment. As shown in FIG. 6, application600 may also include an action bar 602 having a “Save Now” button 602 aand a “Preview” element 602 b. As shown in FIG. 6, application 600 mayalso include a locking portion that allows the representative to selectwhether to freeze (or lock) a portion of the container document. Toselect the freeze (or lock) option, the representative may activate theradio button 604 associated with freezing (or locking) the content. Toallow users to fully customize the container document, therepresentative may select radio button 605 associated with unlocking thecontent.

Upon receiving the application, the representative may select whichcontainer document to be configured in block 504. If the user group hasnot previously configured a container document, the representative mayinitialize a container document to be configured. If the user group hasconfigured one or more instances of container documents, therepresentative may be presented with an interface that enables therepresentative to select from among the container documents toconfigure.

In block 506, a layout may be selected. The representative may selectwhether to optionally freeze (or lock) one or more columns on thecontainer document or allow the user to control all of the content onthe page. For example, FIG. 6 shows a layout tab 601 for enabling arepresentative to select a layout for the container document.

In block 506, colors for the container document may be selected. FIG. 7depicts an exemplary embodiment of an application interface 700including a colors tab 701 to enable a representative, for example, toselect colors for various sections of a container document. As shown inFIG. 7, colors tab 701 may include an element selection portion 702, acolor palette 703, a text box 704, a preview pane 705, and a resetbutton 706. Element selection portion 702 may enable a representative toselect the portion of the container document that is being changed. Forexample, as depicted, a user may select to change the containerdocument's header, background, title, etc. Color palette 703 may enablea user to select a color from those colors presented on the palette forthe selected portion of the container document. Text box 704 may enablea representative to directly enter a known color code into text box 704to select a color for the selected portion of the container document.Preview pane 705 may display a mock-up of the colors selected for thecontainer document. FIG. 8 depicts another embodiment of an applicationinterface 800 to illustrate the colors selected for a containerdocument. Reset button 706 may allow the representative to return allcolors to grey, for example. As shown in FIG. 8, each portion of thecontainer document is identified and a color square indicating theselected color for that portion may be placed adjacent to the identifiedportion. For example, as shown in FIG. 8, the “Title Bar” with a frozen(or locked) column includes a white color square adjacent to the “TitleBar” text.

In block 507, a header and footer for the container document may becustomized. FIG. 9 depicts an exemplary embodiment of an applicationinterface 900 including a header and footer tab 901 to enable arepresentative to customize the header and footer of a containerdocument. As shown in FIG. 9, header and footer tab 901 may include aheader portion 902 that may enable the representative to define a headerto appear at the top of a container document. As shown in FIG. 9, headerportion 902 may include a toolbar 908 that enables the representative toadd an image to the header, add a link to the header, customize the fontfor the header, and/or edit the HTML code comprising the header. Asdepicted, header portion 902 may display a mock-up of the header thatmay appear on the container document. FIGS. 17 and 18 also illustrateexemplary application interfaces that may enable a representative tocustomize the header and footer of a container document.

Header and footer tab 901 may also include a footer portion 903 that mayenable the representative to define a footer to appear at the bottom ofa container document, for example. A footer may include a link 904associated with a privacy page, a link 905 associated with a terms ofservice page, a link 906 associated with a contact us page, and a link907 associated with a service agreement page. Header and footer tab mayalso include an “add a link to the footer” element 909 that may enablethe representative to add custom links to the footer of the containerdocument, for example. As shown in FIG. 9, footer portion 903 maydisplay a mock-up of the header that may appear on the containerdocument.

In block 508, content for the container document may be selected. In anexemplary embodiment, the representative may select from, for example,remote modules, or other modules (e.g., RSS, API-based modules, etc.)that may be included in the container document or create a custom moduleto be included in the container document. FIGS. 10-14 depict variousexample application interfaces for defining the content for a containerdocument using remote modules and/or custom modules. FIGS. 19-21 alsodepict various example application interfaces for defining the contentfor a container document using remote modules and/or custom modules.

In block 509, the container document may be published. As referred toherein, publishing the container document may include any manner ofmaking the container document available to users, including, but notlimited to, saving the container document and indicating to the hostedserver system that the container document is to be available to itsusers. FIG. 15 depicts an exemplary embodiment of an applicationinterface 1500 including a publish tab 1501 to enable the representativeto publish the container document. The representative may select thepublish button 1503 to publish the page. In such an embodiment, the URL1502 of the container document may be displayed. Publish tab 1501 mayalso include an unpublish button 1504 which may enable therepresentative to remove the published container document.

Illustrative Process for Accessing Personalized Container Document

In an exemplary embodiment, users of the user group may access acontainer document that has been configured by the user group, forexample. As shown in FIG. 15, an exemplary URL for a container documentmay be, for example,“http://www.host.com/ig/p/usergroupname/instancename,” where“www.host.com” may represent the domain of the hosted server system,“usergroupname” may represent the user group, and “instancename” mayrepresent a particular container document. A user may also access thecontainer document using, for example, the destination IP address of the“host.” As will be described in greater detail below, a user group mayhave multiple instances of container documents for the users of the usergroup. In an exemplary embodiment, the “/p/” in the URL, for example,may indicate that the particular URL is associated with a containerdocument associated with the user group.

FIG. 16 depicts an exemplary embodiment of a flow chart 1600, whichillustrates a method for serving a container document and/or apersonalized container document to a user of the user group according toan exemplary embodiment. In block 1601, a request for a page may bereceived. As noted above, the request may be a URL request or a requestusing the destination IP address (if known by the user) of the containerdocument. The request may be received by the hosted server system, forexample.

In block 1602, the hosted server system may determine whether therequest is for a container document. As described above, the URL for acontainer document may be, for example,“http://www.host.com/ig/p/usergroupname/instancename” and the “/p/” mayindicate that the URL is associated with a container document associatedwith a partner/user group. In one example, the user group may choose tohide this URL from the users by setting, for example, its own domain(e.g., www.usergroupname.com) to point to this URL via CNAME. The hostedserver system may parse the URL to determine whether the “/p/” ispresent in the URL. If the “/p/” is present, then the hosted serversystem may proceed with serving the container document. If the “/p/” isnot present, then the hosted server system may serve another pageassociated with the URL request. It is to be understood that otherindicators and techniques for recognizing that the URL request is for acontainer document associated with a partner/user group may be used. Forexample, in one example, the URL for a container document may be“http://www.host.com/ig/usergroupname/instancename” and the“/usergroupname/instancename” may indicate that the URL is associatedwith a container document associated with a partner/user group.

In another example, a user may request a URL selected by the user groupsuch as “start.usergroup.net.” Upon receipt of this request, the hostedserver system may determine a true path (e.g.,“partnerpage.host.com/usergroup.net”) associated with this request anddecode the true path to determine the domain name. The hosted serversystem may then look up the domain name in a dynamic table or otherdynamic storage module that is uniquely indexed by partner domain todetermine how to function, for example.

In block 1603, information may be extracted from the URL. The identityof the user group and the particular instance of the container documentmay be extracted from the URL. For example, if the URL has a knownformat as described above, the hosted server system may parse the URL toextract the “usergroupname” and “instancename” strings from the URL.This information may then be used to look-up user group preferencesand/or the personalized container document as will be explained ingreater detail below.

Multiple Points of Entry

In block 1604, the hosted server system may determine whether the useris recognized. The system provided may provide for multiple points ofentry, meaning that multiple different accounts may be used to enable auser to access a personalized partner container document. The user group(e.g., an admin user that sets up the user group container document) mayselect which authentication method(s) (i.e., point of entry) may be usedto authenticate users of the user group. This authentication method mayalso be stored by the hosted server system in the dynamic table or otherstorage module that is uniquely indexed by partner domain. When the usermakes a request for the container document and the domain name is lookedup in this table, the authentication method also may be determined.Thus, the system may determine whether the user is recognized based onthe domain name and the authentication method(s) associated with thedomain name.

For example, a user may have an account with the hosted server system(e.g., Google) that is used for various activities on that hosted serversystem (e.g., email, data storage, personalized home page, etc.). Also,the same user may have an account with the partner whose containerdocument the user is requesting (e.g., the user may be a customer of thepartners). Therefore, if the authentication method to be used isassociated with a particular account, the hosted server system may checkto determine whether it has a record of the user associated with thatparticular account. Where, for example, an account with the hostedserver system may be used to authenticate a user with more than one usergroup, the hosted server system may determine whether the user isrecognized by a particular user group using the domain name andinformation associated with the hosted server system account toauthenticate the hosted server system account to that particular domainname. The hosted server system also may examine one or more cookies, forexample, on the user's system to determine whether the user isrecognized as having an account with the hosted server system if ananonymous/cookie-based authentication method is indicated in the dynamictable that is uniquely indexed by partner domain. If the user is notrecognized or not logged in according to the user group selectedauthentication method for the container document, for example, flowchart 1600 may proceed to block 1605. If the user is recognized orlogged in, flow chart 1600 may proceed to block 1607.

In block 1605, the hosted server system may issue a request to theconfiguration server, for example, to retrieve the preferences of theuser group container document. In an exemplary embodiment, the requestmay include an identification of the user group, other information aboutthe user group, and the instance name of the container document that hasbeen requested. To determine the identification of the user group, thehosted server system may convert the “usergroupname” into a uniqueidentifier that may be associated with an account of the user group. Toconvert the “usergroupname,” the hosted server system may look up thatuser group's identifier in a local map file, for example. Otherinformation associated with the user group may be retrieved usingsimilar look-up techniques. The configuration server may receive thisrequest and then look up further user group information.

In block 1606, the hosted server system may serve a default containerdocument. The hosted server system may receive information regarding thedefault container document into a user group data packet and a displaypreference data packet, for example. The user group data packet mayspecify the layout (e.g., header or no header, fixed column or no fixedcolumns, etc.), skinning preferences (e.g., colors), and the taxonomy,for example. The display preference data packet may specify defaultsettings for each container document, for example. The hosted serversystem may then use this information to serve the default containerdocument to the user. The resulting container document may contain thecontent configured by the user group and the default settings configuredby the user group for any of the content that may be configured by theuser.

In block 1607, the hosted server system may determine whether the userhas personalized the container document in accordance with the user'spersonal preferences. To do so, it may identify the user through theuser group-selected authentication method mentioned above. Specifically,it may enable the user to log-in using the partner account information,the hosted server system account information or some other informationas selected by the user group. To enable this to occur, the accountlog-ins valid for a user to receive a partner container document may bestored at the hosted server system in association with the partnercontainer document data. So, for example, if the partner is a computercompany, Computers4Sale, and they have a partner container document thatis a partner-based Google Personalized Home Page, the user should beable to access the Computers4Sale Google Personalized Home Page bylogging in to Google using a Google account (if the selectedauthentication method authenticates users via an account with the hostedserver system), or by logging into Computers4Sale using a Computers4Saleaccount that Google has stored in its list of users for theComputers4Sale Google Personalized Home Page (if the selectedauthentication method authenticates users via an account with thepartner).

As described above, based on the taxonomy defined by the user group, auser may personalize (e.g., select which modules may be included in thepersonalized container document, apply personal preferences to thosemodules, determine the location of those modules within the containerpage, etc.) the container document associated with the user group. Inone example, a user may personalize the container document withoutlogging in to Google, for example. In this example, the user maycustomize a container document in an “offline” environment (e.g., theuser is not logged-in). The customizations may be stored in a cookie,for example, so that when the user does log in for the first time (orthe first time after making “offline” customizations), the cookie-basedpreferences may be transferred to the server.

If the user has personalized the partner container document, in block1607, instead of the default settings being applied to the partnercontainer document, the user's personal settings may be applied to thecontainer document. The hosted server system may determine whether theuser is recognized and whether the user has personalized the containerdocument simultaneously. If the user has not personalized the containerdocument, flow chart 1600 may proceed to block 1605.

In block 1608, the hosted server system may request the user's personalpreferences. These personal preferences may be stored in a databasesystem that is associated with the hosted server system.

In block 1609, the hosted server system may serve a personalized partnercontainer document. The hosted server system may receive informationregarding the container document in a user group data packet and adisplay preference data packet, for example. The user group data packetmay specify the layout (e.g., header or no header, fixed column or nofixed columns, etc.), skinning preferences (e.g., colors), and thetaxonomy, for example. The user may also add additional non-groupcontent if the user group has configured the container document in amanner that permits the user to do so. The display preference datapacket may specify a user's personal settings for each containerdocument, for example. The hosted server system may then use thisinformation to serve the personalized container document to the user.The resulting personalized container document may contain the contentconfigured by the user group and the personalized settings configured bythe user, for example.

FIG. 22 also depicts an exemplary embodiment of a flow chart 2200, whichillustrates a method for serving a container document and/or apersonalized container document to a user of the user group blocks2201-2203 operating as described above for blocks 1601-1603.

In the example shown in FIG. 22, blocks 2204 and 2205 may operate inparallel. In block 2204, user information may be retrieved. The usergroup may select an authentication method for authenticating users ofthe user group. Thus, to retrieve user information, the hosted serversystem, for example, may the system may check for information theaccount identified by the authentication method. For example, a user mayhave an account with the hosted server system (e.g., Google) that isused for various activities on that hosted server system (e.g., email,data storage, personalized home page, etc.). Also, the same user mayhave an account with the partner whose container document the user isrequesting (e.g., the user may be a customer of the partners).Therefore, based on the authentication method, the hosted server systemmay check to determine whether it has a record of the user being loggedin with the account identified with the authentication method. If theuser group has selected an anonymous/cookie-based authentication method,the hosted server system may examine one or more cookies, for example,on the user's system to determine whether the user is recognized.

In block 2205, default portal data may be requested. To request portaldate, the hosted server system may issue a request to the configurationserver, for example, to retrieve the preferences of the user groupcontainer document.

In block 2206, the hosted server system may determine whether the useris recognized and whether the user has a personalized containerdocument. To do so, it may identify the user through one or more of themultiple points of entry mentioned above. Specifically, it may enablethe user to log-in using the partner account information, the hostedserver system account information or some other information. The hostedserver system may, for example, examine user cookies to determinewhether the user has personalized the container document. The hostedserver system may determine whether the user is recognized and whetherthe user has personalized the container document simultaneously. If theuser has personalized the container document, flow chart 2200 mayproceed to block 2207. If the user has not personalized the containerdocument, flow chart 2200 may proceed to block 2208.

In block 2207, user information may be overlaid onto the containerdocument. To overlay information onto the container document, thecontent selected by the partner/user group, for example, may be combinedwith the user's customizations to form the container document.

In block 2208, the data for the container document may be rendered andthe container document may be served to the user.

Data Driven Design

A user group may have multiple container documents associated with theuser group. In that case, each portal page may be a separate instance.Where, as described above, the URL for each personalized containerdocument is “http://www.host.com/ig/p/usergroupname/instancename,” eachinstance may be uniquely identified by a different “instancename,” forexample. In an example where the URL request isstart.mydomain.net/instancename, each instance may also be identified bya different “instancename.” A user may specifically request an instanceor the hosted server system and/or configuration server system maydetermine which instance to serve to the user by examining cookies onthe user system or other information about the user, for example. Also,the hosted server system may determine which instance to serve based onan IP address, geocoded information, or other external information, suchas information known to the user group but not to the hosted serversystem. Selecting instances in this manner enables a partner to use itsknowledge of its end users to determine which of several pages to servethe end user by default, for example.

Varying Content Based on Geographic Location

One or more instances may be based on varying the content that ispresented to different users. For example, the user group may vary thecontent presented to its users based on a variety of data inputs,including geographic location, user demographics, time of day, time ofyear, etc. In the geographic location example, users on the East coastof the United States may receive an instance associated with the Eastcoast of the United States, while users on the West coast of the UnitedStates may receive a different instance that is associated with the Westcoast of the United States. In another example, the content may bevaried based on the specific city in which the user is located. In suchan example, the hosted server system may determine the location of theuser by determining whether the user has access to a wireless accesspoint (e.g., WIFI or some other wireless protocol). From thatdetermination, the hosted server system may determine the city in whichthe wireless access point is located and serve the user an instanceassociated with that city. Content in that instance may include, forexample, a travel module that shows flights available from the airportnearest to that city. The content may also include, for example aweather module that shows the current weather for that city.

Varying Content Based on Levels of Service

Content may be varied based on, for example, levels of user service. Forexample, where the user group may have users of varying status (e.g.,silver, gold, platinum), the user group may vary the content presentedto its users based on those status levels. In such an example, thehosted server system and/or configuration server system may determinewhich instance to serve to the user by examining cookies on the usersystem or other information about the user, for example. In oneexemplary embodiment, the user group may be associated with an airline,for example. In such an embodiment, the airline may have a frequentflier program and users may be enrolled in that program. If a user hasstatus within that program, the hosted server system may serve the usera container document associated with that status level. For example, ifa user has silver status, the instance associated with silver status mayinclude a module with information on how to obtain a higher statuslevel. If the user has platinum status, for example, the instanceassociated with platinum status may include a module that allows theuser to automatically upgrade to first class on an upcoming flight.

A service provider may have users with various levels of serviceagreements. For example, some users within the user group may have an“at-home” service agreement while other users within the user group mayhave a “basic” service agreement that requires the user to send the itemin for repairs. In such an example, the instance associated with the“at-home” service agreement may include a module for setting up anat-home service call. The instance associated with the “basic” serviceagreement may include a module that provides instructions on where tosend the item for repairs based on the user's geographic region, forexample.

Subscription Based Content

Partner/user groups may also vary content based on subscriptions. Forexample, some user may subscribe to “premium” content. Those users thatsubscribe to the “premium” content may be served an instance containinga module including the “premium” content. Also, users may subscribe tocontent-based modules. For example, the partner may offer a music moduleand a subscription to the partner's music module may enable the user tochoose certain selections of music to hear based on subscriptions. Also,within the music module, the partner may offer different subscriptions.For example, one subscription may permit an end user to listen to music,while another may permit the user to listen to and download music. Inthese examples, the partner may charge the user a fee for thesubscription, thus enabling the partner to monetize modules within thecontainer document.

Selective Internationalization

Instances of a partner container document may be associated withdifferent languages. In such an embodiment, the hosted server systemand/or the configuration server system may, for example, determine thelocation of the user as described above and serve an instance of acontainer document that is in a language associated with the location ofthe user. For example, users in the United States may be served aninstance of container document that is in American English, users in theUnited Kingdom may be served an instance of a container document that isin British English, and users in France may be served an instance of acontainer document that is in French. Also, partner or user profiles mayidentify a language preference and such preferences may be used tointernationalization the container document based on such content.Different versions of the container document may be provided for thedifferent languages as well.

The multiple instances for a user group may be based on a commontemplate. For example, in the example described above regarding theairline module, each instance of the container document may include themodule showing flights, with the content within the module varying basedon the geographic location. In another embodiment, the multipleinstances may not be based on a common template, with each instancebeing unique.

Illustrative Configuration User Interface

As described above, a representative associated with the user group mayconfigure the container documents for the users of the user groupthrough a web application. Such an application may include a userinterface for configuring and/or defining the container document may beinteractive. Such an interface would permit the representative to view afully-functional preview of the actual content that is not yetpublished. The interface may also permit the representative to edit thecontent within the fully-functional preview.

Live Container Document Preview

There may also be many interconnected components of the user interface.When changes are made using one of the components, the other componentsmay need to be synchronized. To synchronize the components of a userinterface, the components may observe each other to recognize thechanges and update accordingly. The source of the change (e.g., the pagecontent tab) may “push” the change to all observers. For example, if acheckbox for a module is unchecked in a module taxonomy selectionportion on the available content tab, the module should disappear in themodule taxonomy selection portion on the selected modules tab. In suchan example, the checkbox may “push” the change to the selected modulestab.

Observers may also actively poll the sources of changes for changes tothe interface. For example, the components of the user interface mayperiodically poll the backend layer to determine whether any of thefiles associated with the user group have changed. If so, the changesmay be updated immediately in the other components of the interface. Thefollowing examples may be considered. In one example, when a user isediting the colors of the container document using the colors tabdescribed above, all of the components of the colors tab may beregistered with a central party (i.e., an event registrar) for aninterest in an event to “synchronize color.” When one of the componentsin the colors tab reflects a change, the component may notify the eventregistrar, which may, in turn, notify all of the components registeredfor the “synchronize color” event.

Search Box within Container Document

As described above with regard to FIG. 2, in various exemplaryembodiments, a container document may include a search box. In suchembodiments, a search box may be associated with a host of the containerdocument. When a user of the container document enters text into a textfield and executes a search, search results may be returned to the user.In some instances, the search results may include links associated withadvertisements. If the user subsequently click on one of the linksassociated with an advertisement, the host of the container document maycompensate the user group. The host may credit an account of the usergroup, for example. The manner of revenue sharing between the host anduser group may involve a percentage of revenue, a flat fee arrangement(e.g., a specific amount per click), or other arrangements known in thisfield.

Example Hosted Server System for Serving Container Documents

The operation of a hosted server system may involve a number of tasksand units as described in the attached patent application. Forbackground, a brief description of units that may be used to serve thecontainer document is provided relative to FIG. 1( c). There, a hostedserver system 10 includes a plurality of units which may include acontainer server 12, a module server 14, a specification server 16, aback end server 18, an analysis unit 28, a module creation server 32, asyndication server 34, an advertisement server 36, a geocode server 37and/or a map server 39.

Other systems connected to network 26 may comprise one or more usersystems 22, one or more remote source systems 24, one or more moduledeveloper systems 30, one or more content providers, and one or moresyndication recipient servers 38. In addition, one or more databasesystems 20 may operate in conjunction with the various units of hostedserver system 10.

Container server 12 (e.g., a web server) may serve the containerdocument to user systems 22 over network 26. Container server 12 maytake data and/or instructions and may formulate a container fortransmission over the network to the user system 22.

Module server 14 may provide data from modules to container server 12for incorporation into a container document. It should be appreciatedthat in one embodiment, container server 12 and module server 14 maycomprise a single unit performing both functions. Module server 14 mayprovide data for the container document by interpreting and/or parsinginstructions in the module specification associated with the module.According to one embodiment, module server 14 may serve the modulecontent to the container document through the use of a browser IFRAME.An IFRAME may be generally understood to be an independently operatedbrowser window instance inside the container document. One advantage ofan IFRAME is that is protects the container document from the IFRAME'scontent and vice versa, e.g., JavaScript on the container document maynot be permitted to access any JavaScript code in the inner IFRAME (samefor CSS, DOM, or cookie objects).

Multiple Choices of Module Formats

To expedite display of container documents, modules may be displayedinline within the container document. Inline display may be understoodas referring to display with other document elements. One example is adisplay generated from code for HTML in the body according to HTMLstandards. In one embodiment, module server 14 or some other componentmay determine whether the module is deemed trusted prior to including itin the container document inline due to the risks of various securityissues an inline module could create. According to one embodiment, themodule may incorporate an indicia of approval (e.g., digitalcertificate) issued by the container module or an entity associated withthe container module as described in detail below. If the indicial ofapproval is present, module server 14 may render the data from a modulefor inline presentation in the container document.

Specification server 16 provides the module specification file to moduleserver 14. The module specification may be cached and stored in adatabase accessible to the module server 14 and/or specification server16 or may be retrieved from a location associated with the specificationas detailed later. For example, specification server 16 may reside on aremote source system 24. In addition, specification server 16 may beconnected to module server over a network with the module specificationlocated at another location on the network accessible to specificationserver 16.

Backend server 18 may be provided for interacting with one or moredatabases (e.g., large or dynamic databases of information). Forexample, for a news module that obtains frequent updates and demands aflow of data, (e.g., from an RSS feed), backend server 18 may format thedata into HTML for the container.

In one specific example, a person may create a module (e.g., a mapsmodule), such as one that uses an application program interface (API) toan existing mapping program to create a module to display a map ofdowntown Mountain View, Calif. The module may comprise an XMLspecification file or module specification file stored on aspecification server. The specification server may comprise any server,including one on the site from which the container page is hosted or anyother site. The user or another person may then include this new moduleon a personalized homepage (container document). The server that servesthe container document may operate as the module server and the serverthat generates the mapping data through an inquiry from its API may beconsidered to be the backend server.

According to one embodiment of the present invention, analysis unit 28may analyze modules at various times (e.g., when the module is firstselected by a user, each time the module is called by a container forinclusion or at any other time determined to be advantageous for safetyand security and other times). Analysis unit 28 may perform a number ofactions, including comparing the module with a list of disapproved ordangerous modules or a list of approved modules. The comparison mayinvolve exact or substring (e.g., prefixes, suffixes and regularexpressions) matching by name or location (e.g., URL), contents of thespecification, contents of the location where the specification resides,or information that may be ascertainable about the module. Analysis unit28 may take one or more actions in response to a determination that themodule is disapproved or dangerous, including, for example, silentlyblocking the request, (i.e., providing a generic error), blocking therequest with an error that explains the reason it was blocked orredirecting the request to a different module specification that hasbeen determined to be safe and related to the disapproved module (e.g.,another module that relates to maps, if the first one was a disapprovedmapping site or a module that includes the keyword “basketball” if thedisapproved module was a basketball module). For example, throughredirection, the URL of the original module may be passed to the “safe”module. The safe module may then use a proxy server, as described below,to retrieve the original URL's content. Developers may then replace theerror handler to fix small bugs in the original module to be able todisplay the content of the original module. In another embodiment,analysis unit 28 may parse the module content to determine whether it issafe, such as by compiling JavaScript or other scripts contained in themodule to try to identify unsafe or undesired actions the module mayperform.

One or more content providers 31 may be provided. Content providers 31may provide the content to be served in modules and/or may providemodules to be served to end users. Examples of a content providerinclude but are not limited to a provider of a module, a news feed, asource of traffic information, a source of financial information, asource of entertainment information.

One or more module creation servers 32 may be provided. This server mayoperate as a “wizard” to enable module creators to create a modulethrough an interactive process controlled by module creation server 32.For example, module creation server 32 may provide a series of userinterfaces that enable the module creator to provide inputs that arethen used by the module creator to automatically generate a modulespecification. For example, various module specification templates maybe provided with corresponding inputs. Module creation server 32 maythen take inputs supplied by a module creator, insert them into thetemplate and then generate the module specification for the module. Apreview, testing and debugging function may also be offered as part ofthis “wizard.” This web tool and/or downloadable application may bedownloadable as well so it may be installed and operated at any node onthe network. In various embodiments of the invention, the module creatormay be a representative associated with a user group. Also, the modulecreator may be an example of a content provider.

A syndication server 34 may prepare data for transmission to one or moresyndication recipient servers 38 related to modules. Syndication server34 may receive a request for a module and/or module content and deliverthat module or content to a syndication recipient server 38 over network26. Syndication server 34 may reside at hosted server system 10 or atanother location on the network. For example, if an operator of a sportsweb site (an example of a syndication recipient system 38) desired toinclude a maps module created by a remote source system 24, it may do sothrough a request to syndication server 34. Syndication server 34 maythen cooperate with module server 14 to generate data for the containerdocument (here the sports web site page of the syndication recipientsystem 38). That may involve retrieving the module specification fromremote source system 24, supplying preferences received from thesyndication recipient server 38 (e.g., city information for the sportsteam of a page being displayed) and/or generating data for thecontainer. It is also possible that the data may be rendered atsyndication recipient server 38 into its container document in either anIFRAME or inline. Syndication server 34 may thus syndicate modulesaccessible to it. It may do so based on requests for specific modules orother criteria it determines (e.g., content matches, keyword matches,monetary values associated with modules and/or syndication requesters,etc.)

Ad server 36 may provide advertisements associated with modules tocontainers. For example, an advertisement may be incorporated withmodule data when data is delivered to a container document. Ad server 36may operate with syndication server 34 to deliver advertisements tosyndication recipient servers 38 based on a syndication request for amodule. The advertisements may be selected by ad server 36 based on awide variety of criteria, including, but not limited to, therelationship between the content of or information about the container,module, other modules in the container, syndication recipient serverinformation, monetary elements/relationships related to any of theforegoing and/or combinations thereof. Ad server 36 may comprise theGoogle AdSense system, according to one embodiment of the presentinvention. Ad server 36 may operate as described in one or more of thefollowing patent applications.

A geocode server 37 may be provided to generate geocode information fromlocation descriptions as is known in the art. A geocode server 37 maygenerate latitude and longitude numeric values from geographiclocations.

A map server 39 may generate map output. Mapping systems, such as GoogleMaps and Google Earth, may be used to generate this data.

One or more database systems 20 may be provided that store, in anynumber of ways, container information, module specifications and/orrelated information, formatting data, per-user and per-module preferencedata, remote module ID data, remote module location reference data,advertisement data, advertiser data, content/monetary data, syndicationrecipient data, templates for modules, inputs for modules, lists oftrusted and untrusted modules, approval criteria and related informationand/or any other information used by the modules to operate as describedherein. While a single database structure is shown for database system20, it is well understood that the data may be stored at a number oflocations and in one or more systems.

In addition, what is shown as user system 22 may also operate as aremote source system 24 and/or a module developer system 30. In otherwords, one computer system may operate in different capacities: as auser system, as a remote source system, as a syndication server, as atarget content server, and/or a module developer system. In addition, asexplained in greater detail below, each of the modules depicted withinhosted server system 10 may also be disposed at a user system 22, aremote source system 24, or a module developer system 30. Similarly,databases 20 may be associated with each of the modules depicted withinFIG. 1( c) depending upon the configuration desired.

The present disclosure is not to be limited in scope by the specificembodiments described herein. Indeed, other various embodiments of andmodifications to the present disclosure, in addition to those describedherein, will be apparent to those of ordinary skill in the art from theforegoing description and accompanying drawings. Thus, such otherembodiments and modifications are intended to fall within the scope ofthe present disclosure. Further, although the present disclosure hasbeen described herein in the context of a particular implementation in aparticular environment for a particular purpose, those of ordinary skillin the art will recognize that its usefulness is not limited thereto andthat the present disclosure may be beneficially implemented in anynumber of environments for any number of purposes. Accordingly, theclaims set forth below should be construed in view of the full breadthand spirit of the present disclosure as described herein.

1. A method comprising: providing a customizable content documentassociated with a first entity; enabling a second entity to specifycontent to be included for users associated with the entity in thecustomizable content document; and delivering the customized contentdocument incorporating the specified content in a secure manner to usersassociated with the second entity.
 2. The method of claim 1, wherein thesecond entity selects content from a source other than the first entity.3. The method of claim 1, wherein the selections are stored on ascalable storage system platform.
 4. The method of claim 1, wherein thecontent is dynamic.
 5. A method comprising: receiving one or moreselections associated with a user group, the one or more selectionsidentifying content to be served to users associated with the user groupfor one or more container documents; and serving a user a containerdocument, the container document including content identified by the oneor more selections for the user group with which a user is associated,the content being incorporated securely into the container document. 6.A method comprising: receiving one or more selections associated with auser group, the one or more selections identifying content to be servedto users associated with the user group for one or more containerdocuments; and transmitting the selections to a container server systemthat serves a container document to users of the user group based on arequest for the content.
 7. A system that serves content in a containerdocument, comprising: a first server to receive a request for acontainer document, determine whether the request is for a containerdocument associated with a user group, request configuration informationfrom a configuration server based on a determination that the request isfor a container document associated with a user group, receive theconfiguration information from the configuration server, and serve therequested container document using the configuration information,wherein the configuration server enables configuration of at least aportion of a container document, and wherein the container document isassociated with a user group.
 8. The system according to claim 7,wherein the server further determines whether a requestor of the requestfor the container document is known.
 9. The system according to claim 8,wherein the server retrieves information associated with the requestorbased on a determination that the requester is known.
 10. The systemaccording to claim 9, wherein the server serves the requested containerdocument using the configuration information and the informationassociated with the requestor.
 11. The system according to claim 7,wherein the container document includes at least one module comprising acontent element and one or more optional preference elements to enablethe second server to provide preferences to the module.
 12. The systemaccording to claim 11, wherein the server further determines whether arequestor of the request for the container document is known.
 13. Thesystem according to claim 12, wherein the server retrieves informationassociated with the requester based on a determination that therequestor is known.
 14. The system according to claim 13, wherein theserver serves the requested container document using the configurationinformation and the information associated with the requestor.
 15. Theserver system according to claim 7, wherein the configuration servercomprises a first layer to provide a user interface to a user system andreceive data from the user interface.
 16. The system according to claim15, wherein the configuration server further comprises a second layer toverify the data received from the user interface by the first layer andconvert the data into a predetermined format.
 17. The system accordingto claim 16, wherein the configuration server further comprises a thirdlayer to execute instructions.
 18. The system according to claim 17,wherein the configuration server further comprises a fourth layer tointeract with one or more of the first, second, and third layers. 19.The system according to claim 15, wherein the first layer to uploadsdata to a storage system.
 20. The system according to claim 7, whereinthe configuration information is defined by the user group.
 21. Thesystem according to claim 20, wherein the information associated withthe requestor comprises preferences of the requester.
 22. The systemaccording to claim 20, wherein the configuration information definescontent available for inclusion in a portion of the container documentand options for configuring the content, and wherein the informationassociated with the requestor is based on the options for configuringthe content.
 23. The system according to claim 7, wherein the containerdocument comprises a module to receive search terms and provide searchresults based on the search terms.
 24. The system according to claim 23,wherein the search results include advertisements, and wherein the usergroup receives payment when the advertisement is acted upon.
 25. Amethod, comprising: receiving a request for a container document;determining whether the request is for a container document associatedwith a user group; requesting configuration information based on adetermination that the request is for a container document associatedwith a user group; receiving the configuration information; and servingthe container document using the configuration information, wherein theconfiguration information defines at least a portion of the containerdocument associated with the user group.
 26. The method according toclaim 25, further comprising: determining whether a requestor of therequest for the container document is registered.
 27. The methodaccording to claim 26, further comprising: retrieving informationassociated with the requestor based on a determination that therequestor is registered.
 28. The method according to claim 27, furthercomprising: serving the requested container document using theconfiguration information and the information associated with therequester.
 29. The method according to claim 25, wherein theconfiguration information is defined by a representative of the usergroup.
 30. The method of claim 1, further comprising: enabling thesecond entity to specify an authentication method to authenticate theusers associated with the second entity.
 31. The method according toclaim 1, further comprising: storing a reference to the customizedcontainer document in a dynamic table that is maintained by the firstentity.
 32. The method according to claim 5, the one or more selectionsfurther identifying a domain name to be associated with the user group.33. The method according to claim 32, further comprising: storing thedomain name in a dynamic table.
 34. The method according to claim 5, theone or more selections further identifying an authentication method toauthenticate the user associated with the user group.
 35. The methodaccording to claim 34, further comprising: storing the authenticationmethod in a dynamic table.
 36. The method according to claim 6, the oneor more selections further identifying an authentication method toauthenticate the user associated with the user group.
 37. The methodaccording to claim 6, the one or more selections further identifying anauthentication method to authenticate the user associated with the usergroup.
 38. The system of claim 8, wherein to determine whether arequestor is known, the server determines a previously storedauthentication method to authenticate users associated with the usergroup and authenticates the requester based on the previously storedauthentication method.
 39. The method of claim 25, wherein thedetermining whether the request is for a container document associatedwith a user group includes retrieving information associated with adomain name, wherein the domain name is selectable by the user group,and the information associated with the domain name is stored in adynamic table.